Tech Arsenal 1/Tech Arsenal (Arsenal Computer).ISO/tek-20/arrlnd.zip/HEAVEN

Text File | 1992-01-06 | 8KB | 156 lines

                        A MARRIAGE MADE IN HEAVEN -

               PACKET RADIO AND THE NATIONAL TRAFFIC SYSTEM

      By Steve Czaikowski, WB4ZTR and Deni Watters, WB0/TAX

This procedure is to assist both the BBS SYSOP and the NTS operator in
the use of the packet radio network.  Your assistance in following
these procedures will result in a smoother liaison between packet and
the ARRL National Traffic System.

A packet radio BBS forwards its traffic (mail) through the use of a
forwarding file which, for NTS purposes, includes a list of Zip Codes and 5
letter State Designators.  The designators consist of the letters "NTS"
followed by the two letter Postal abbreviation for the State.  For example,

            "NTSCA" means "route this message to California"
            "NTSNC" means "route this message to North Carolina"
            "NTSBC" means "route this message to British Columbia, and
so on.

A properly addressed packet message headed for Hampton, VA would look like
this:

                            "ST 23666 @ NTSVA"

Regardless of where this message entered the packet system, it would end up
in Virginia.  Once inside the state, the "NTSVA" is stripped, and the
traffic is forwarded to the closest BBS serving the Zip Code of the
addressee.  A NTS traffic handler in the area must reclaim the traffic from
the local BBS and deliver it to the addressee.

Traffic addressed to Canada would include the appropriate Postal Code in
place of the Zip Code.  Note that the Canadian Postal Codes are 6 digits,
with alternating numerals and letters.  A piece of traffic destined for
Hamilton, Ontario, Canada would look like this:

                          ST M1P1T7 @ NTSON

The space normally placed between the "M1P" and the "1T7" is not used.

If you are originating traffic destined for somewhere within your
State or Province (called in-state traffic), the "@ NTSVA" is not required.
The message header will simply be "ST 23666" (for Hampton, VA), or "ST
M1P1T7" (for Hamilton, ON).  If you should elect to use the "@ NTSVA" for
in-state traffic, it will be stripped at the first BBS in line.

It is Very important to use only the recognized 2-letter State and Province
abbreviations.  Traffic sent to "@NTSMDC" will not go anywhere!  "MDC" is
an ARRL Section abbreviation (for Maryland-District of Columbia), and not a
2-letter State or Province.  The traffic will not move because "MDC" does
not appear in the forwarding file of some BBSs.  The listing of recognized
2-letter abbreviations appears in the ARRL's Public Service Communications
Manual as well as in this Net Directory.

                HOW TO ORIGINATE NTS TRAFFIC AT A BBS

Once logged in or connected to a BBS, you will be left at the prompt.  This
is normally a greater than (>) sign, and is the indication that the BBS is
ready for further instructions.

1.  Send the ST command to (S)end (T)raffic, followed by a space, the Zip
Code (or Canadian Postal Code) of the addressee, a space, the @ sign, a
space, and the NTSXX of the state or Province, (where xx is the 2-letter
abbreviation for the State or Province).   The transfer would look like
this:

WA4ONG BBS>                  ST 10016 @ NTSME    (Traffic for Maine)

2.  After entering the command information, you will be prompted for the
subject of the message.  At the subject line, enter the city or town,
followed by the first 6 digits of the phone number, like this:

QTC Bangor 403/234      (403 234 are the first six digits of the telephone
                        number, including Area Code - the use of "QTC" is
                        optional.

3.  Once the subject is entered, you will be prompted for the actual
message.  Upon reaching this point, you should send the traffic according
to the standard ARRL format, including message, number, precedence, check,
originating station, callsign, city and state of origination and date.  You
may separate the preamble, address, text and signature with an <enter> key
to make the packet easier to read.

Please remember that even though you may be originating the traffic on
packet, it is likely that the message may be relayed at some point by other
NTS methods -- CW, SSB, and Amtor for example.  Keep the check (word count)
to less than 25 words.  An example of a proper message preamble as
originated on packet is:

                   NR 1 R HXG WB4ZTR 8 HAMPTON VA FEB 1

4.  After entering the signature, end the message with either a CTRL Z or
/EX.  This will complete the sending of the traffic.

You can check your work by sending either "L@ NTSxx, where "xx" is the 2-
letter abbreviation for the State or Province destined to receive your
traffic), or "LT", which stands for (L)ist (T)raffic.  LT will show you all
Traffic (T) on the BBS.  You may also read the traffic by sending (R)ead
and the BBS-assigned message number.

                   HOW TO REMOVE NTS TRAFFIC FROM A BBS

There are several things you should consider prior to removing NTS traffic
from a BBS, there are several things you should consider.  Is the traffic
for your area?  Is the addressee best served if the traffic is removed at
your location?  If left, will the traffic continue to be forwarded by the
packet network?  If the traffic is destined for another location, it may be
better for you to just leave it along, but keep an eye on it to make sure
that it eventually does move.  Traffic listed on a BBS by Zip Code probably
will automatically be forwarded to its destination.

If you decide to remove the traffic, here is how you should proceed:

1.  Issue the LT command to the BBS and check all traffic on the board.
You should note the BBS-assigned message number of the traffic listed that
you want to remove.

2.  Turn on your printer and direct the copy to it, or save it to disk.
This is important so that you will have a copy of the message to view when
you relay or deliver the traffic.

3.  Issue the (R)ead command, followed by the BBS-assigned message number
of the traffic you want to take.  Check your printer or disk copy to be
sure you have it saved.

4.  Once you have read the message and verified your copy, then issue the
(K)ill (T)raffic command (KT) followed by the BBS message number of the
traffic you took, to kill the traffic.  You MUST use the BBS assigned
message number to kill the traffic.  Do not confuse the BBS message number
with the message number in the preamble of the message.

5.  Relay or deliver the traffic.  This a good time to send a message back
to the originating operator telling him when, where, and by whom the
message was delivered, if he so requested.

If you are interested in handling traffic, whether you are wanting to break
into it for the first time, or have been doing it for years, please advise
your Section Traffic Manager (STM) which BBS you monitor and how often you
check into that BBS.  Your STM's identity can often be found in the QST
Section News column for your Section, or it can be obtained from your
Section Manager, found on page eight of every issue of QST.

Daily monitoring of BBSs is essential if we are to maintain quick
deliveries of traffic.  Notify the SYSOP of your local BBS if you are
interested in handling traffic, and provide him or her with a list of Zip
Codes that you are willing to accept traffic for.

Make a habit of using the List Traffic (LT) command whenever you log onto a
BBS.  This will insure that there is no traffic there that you can properly
handle.

Be sure to contact your Section Traffic Manager if you need further information
on traffic handling.

*eof